fix: correct release update times and asset markers - #280
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Included review availability: Your plan provides up to 8 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughChangesThe release refresh now records added or changed asset IDs. Repository timelines use effective release times that include asset updates. Download rows and repository headers display asset-update indicators for unread releases. Release asset updates
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This PR updates release and asset timestamps and adds asset update markers; no actionable merge-blocking risk remains after normal checks and review. Sequence Diagram(s)sequenceDiagram
participant GitHubReleaseAssets
participant ReleaseRefresh
participant ReleaseTimeline
participant ReleaseCard
GitHubReleaseAssets->>ReleaseRefresh: provide refreshed release assets
ReleaseRefresh->>ReleaseRefresh: compute updated_asset_ids
ReleaseRefresh-->>ReleaseTimeline: provide changed releases
ReleaseTimeline->>ReleaseTimeline: select latest effective release
ReleaseTimeline-->>ReleaseCard: pass assetId and update metadata
ReleaseCard->>ReleaseCard: display “Asset updated” when unread
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
资产已更新/Asset updatedmarker in both release viewsValidation
npm run lint(passes with one pre-existing warning inVectorSearchSettings.tsx)npm run test:run(299 tests passed)npm run build(passes)Fixes #263
Summary by CodeRabbit
New Features
Bug Fixes